UUCP-ST Documentation Version 1.01, 10 July 1996 ========================== Copyright ========= This entire package, hereinafter referred to as "UUCP-ST" and/or "UUCP" is copyright 1996 by Rich Tietjens and FTI Consulting. Limited rights are granted to use the software without modification. The programs are released without warranty of any kind, including fitness for a particular purpose. The package should contain the following: AGE_HIST.PRG Controls the size of the message history file EMAILOUT.PRG Exports Fido netmail to Internet email EMAIL_IN.PRG Imports Fido netmail from Internet email NEWS_IN.PRG Imports Fido echomail from Usenet newsgroups NEWS_OUT.PRG Exports Fido echomail to Usenet newsgroups PURGE.PRG (Unsupported) Kills selected messages STATS.PRG Reports userbase statistics UNLOCK.PRG Deletes "orphan" files in the NOS tree EXAMPLE.CTL Commented example control file for UUCP-ST WORMHOLE.CTL Commented example control file for Wormhole WORMHOLE.PRG Imports and exports Fido packets via Internet email HELP.TXT Sent to new users & users who send a "help" message HISTORY.TXT Development history of UUCP-ST INSTALL.TXT Quick Start installation instructions TO-DO.TXT To-do list (and known bug list) UUCP_DOC.TXT This document WARNING.TXT Warning text sent to users trying to access Archie/Ftpmail servers Terms of Use ============ You are permitted to use the software without registration for a period of 90 consecutive days from the date of first installation. No restrictions are placed on function or use of unregistered versions; however, no support will be offered to unregistered users beyond bug fixes which would be released in the normal course of events. The Wormhole program is provided as freeware. Sysops are requested to send email to me at one of the provided addresses (see below), or a nice picture postcard via snail mail, to register, but no functions are disabled in the unregistered release. Registered Wormhole sysops will receive priority for requested features, and a warm fuzzy feeling inside. Priveleges of Registered Users ============================== UUCP-ST is a shareware package which will be undergoing continuous development and upgrade. Users of the package who register will be given special consideration for adding desired features, direct email contact, and special ftp access which will not be available to unregistered users. How To Register =============== Send email to starship@3rdplanet.com (Rich Tietjens), or netmail to Rich Tietjens on 51:205/311.0@atarinet.ftn or on 90:304/6.0@nest.ftn, or post a letter to: Rich Tietjens 8495A SW Hemlock Tigard, OR 97223 USA Registration costs US$15. You will receive your key file and the latest version of UUCP-ST via Internet email, or on floppy disks if you prefer. Additionally, you will be given a password that will allow you to log onto the STarship ftp server with direct access to the UUCP-ST release folder; this level of access is not available to unregistered users or the general public. Finally, you will also be given special consideration when asking for additional features in the programs that make up UUCP-ST. System Requirements =================== Before installing UUCP-ST, you need to make sure that you have the required hardware and software. Hardware: UUCP-ST should run on any ST/TT/Falcon compatible with at least 1 megabyte of RAM and adequate hard drive space for the working files. Software: This is a little more complex; you must have the following: (1) A working NOS setup (to allow access to your Internet account, both email and news) (2) A working Fido-compatible mail tosser and reader. UUCP-ST was developed using NOS-POP3, Jetmail, LED and Octopus. Any version of NOS that works with your provider should be fine. IOS can be expected to work, but has not been tested; likewise, any Fido-messagebase-compatible message reader or BBS should work. Installation ============ (1) It is assumed you have already unZipped the archive. If you haven't, and you are reading this direct from ST-Zip, complete Step 2 and then unZip all the files into the directory created there. (2) Create a folder wherever it is convenient for your particular system. The suggested folder name is "UUCP" but that is not a requirement. (3) Move all of the UUCP-ST files into the folder you just created. (4) Copy EXAMPLE.CTL to UUCP.CTL in the same folder. (5) Edit UUCP.CTL to conform to your particular system. The provided example file is heavily commented; the comments may be deleted from the UUCP.CTL file, but it is strongly suggested that you retain the unmodified Example file for reference. (6) You must also edit your AREAS.BBS file to add all the newsgroups as Fido-style message bases. Make sure all of the folders and message base files that you will be referencing with UUCP.CTL actually exist! When the News Manager is completed, it will take care of this automatically, but in this early release, you are responsible for manually creating folders. (7) Run your mail tosser in "maintenance" mode before running either of the News programs for the first time. This will ensure that all of the message areas exist and are the expected size. (8) Decide how often you wish to run the various maintenance programs that make up UUCP-ST; once daily is the suggested minimum, but all of them will run faster if they are run more often (as they have less to do each time, the more often they run). Here is the list of programs (and commands) that we run at STarship each time we call the Internet: Jetmail import scan pack bundle Wormhole EmailOut News_Out Unlock NOS -d i:\oasis -s 64 startup.nos Age_Hist Wormhole Email_In News_In Jetmail import scan pack bundle You'll need to create a batch file, (if you're running a CLI) or a function (if you're running Semper) to execute the desired programs in the correct order. NOTE: If you use Wormhole, it MUST be executed before Email_In, because there is no text for Wormhole to process after Email_In runs! Support ======= Should you need assistance, contact me at the above-listed email address(es) and, regardless of your registration status, I'll try to get your setup working. After all, you can't test the programs if you can't make them work!